Skip to content

Hycom documentation purge#3157

Open
jdkublnick wants to merge 5 commits intoufs-community:developfrom
jdkublnick:text/hycomdocpurge
Open

Hycom documentation purge#3157
jdkublnick wants to merge 5 commits intoufs-community:developfrom
jdkublnick:text/hycomdocpurge

Conversation

@jdkublnick
Copy link
Contributor

@jdkublnick jdkublnick commented Mar 20, 2026

Commit Queue Requirements:

  • This PR addresses a relevant WM issue (if not, create an issue).
  • All subcomponent pull requests (if any) have been reviewed by their code managers. N/A
  • Run the full Intel+GNU RT suite (compared to current baselines), preferably on Ursa (Derecho or Hercules are acceptable alternatives). Exceptions: documentation-only PRs, CI-only PRs, etc. N/A --> doc PR
    • Commit log file w/full results from RT suite run (if applicable).
    • Verify that test_changes.list indicates which tests, if any, are changed by this PR. Commit test_changes.list, even if it is empty.
  • Fill out all sections of this template.

Description:

Purging hycom documentation from User's Guide.

Commit Message:

* UFSWM -Purging hycom documentation from User's Guide. 

Priority:

  • Critical Bugfix: Reason
  • High: Reason
  • Normal

Git Tracking

UFSWM:

Sub component Pull Requests:

  • None

UFSWM Blocking Dependencies:

  • Blocked by #
  • None

Documentation:

  • Documentation update required.
    • Relevant updates are included with this PR.
    • A WM issue has been opened to track the need for a documentation update; a person responsible for submitting the update has been assigned to the issue (link issue).
  • Documentation update NOT required.
    • Explanation:

Changes

Regression Test Changes (Please commit test_changes.list):

  • PR Adds New Tests/Baselines.
  • PR Updates/Changes Baselines.
  • No Baseline Changes.

Input data Changes:

  • None.
  • PR adds input data.
  • PR changes existing input data.

Library Changes/Upgrades:

  • Required
    • Library names w/versions:
    • Git Stack Issue (JCSDA/spack-stack#)
  • No Updates

Testing Log:

  • RDHPCS
    • Orion
    • Hercules
    • GaeaC6
    • Derecho
    • Ursa
  • WCOSS2
    • Dogwood/Cactus
    • Acorn
  • CI
  • opnReqTest (complete task if unnecessary)

@github-project-automation github-project-automation bot moved this to Evaluating in PRs to Process Mar 20, 2026
@jdkublnick jdkublnick changed the title Text/hycomdocpurge Hycom documentation purge Mar 20, 2026
@jdkublnick jdkublnick marked this pull request as ready for review March 20, 2026 18:28
jdkublnick and others added 2 commits March 20, 2026 16:49
Co-authored-by: Gillian Petro <96886803+gspetro-NOAA@users.noreply.github.com>
Co-authored-by: Gillian Petro <96886803+gspetro-NOAA@users.noreply.github.com>
- Coupled :term:`ATM` - :term:`MOM6`- :term:`WW3` - :term:`CMEPS`
* - HAFS-ALL
- Coupled :term:`CDEPS` - :term:`ATM` - :term:`HYCOM` - :term:`WW3` - :term:`CMEPS`
- Coupled :term:`CDEPS` - :term:`ATM` - :term:`WW3` - :term:`CMEPS`
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- Coupled :term:`CDEPS` - :term:`ATM` - :term:`WW3` - :term:`CMEPS`
- Coupled :term:`CDEPS` - :term:`ATM` - :term:`MOM6` - :term:`WW3` - :term:`CMEPS`

Doesn't make sense to have a hurricane test with no ocean model ;) MOM6 replaces HYCOM in tests that aren't deleted.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There are tests with "hafs" in the name which do not include OCN. There are several ATM only as well as an ATM-WAV.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, we list ATM and ATMW as separate configurations in this table near the top, and HAFS, HAFSW, HAFS-MOM6W, and HAFS-ALL are each listed, but @jdkublnick we are missing HAFS-MOM6. And I would think HAFS-ALL would switch from HYCOM to MOM6, right? That's the edit I was trying to make here. But I'm also wondering if this entire table may have outlived its usefulness... I mean, in theory, people could build experiments for any combination of WM components if they wanted, and the existing list in CMakeLists.txt just keeps expanding. It might make more sense to nix the list and send them to the relevant file for the list of APPs. And/or to rt.conf to see what particular tests are compiled with which -DAPP flag. If we keep the list, I think the key for @jdkublnick is going to be to check the tests for each relevant compile in rt.conf rather than just taking out HYCOM and assuming it'll still be valid and non-redundant (unless you can think of a better way?).

Copy link
Collaborator

@gspetro-NOAA gspetro-NOAA Mar 21, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jdkublnick It looks like the details on each APP and what components are available with each are listed in cmake/configure_apps.cmake. Maybe Denise has a different suggestion, but that looks to me like the clearest place to get the full list of APPs and corresponding components. It might be best just to go over this whole table and makes sure everything's covered and accurate/up-to-date.

Comment on lines 353 to +357
* - hycom1_25.nc
- vertical coordinate thickness defining 25 vertical levels
- 9.00, 5.00
-
* - hycom1_75_800m.nc
* - hycom1_75_800m.nc
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@DeniseWorthen Are these two files used by MOM6 despite their name? They're listed in the MOM6 section of the docs.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, despite the name, they are used by MOM6 to set the vertical grid.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It could be good to look at changing that... Not a pressing issue, but maybe next time there's a new input data directory for other reasons, it could be considered? 🤔 Not sure to what extent changing the naming would have an outsized impact on other code/tests tho, so if we need to keep it as-is, that's fine.

Comment on lines -958 to -960
* - hycom_YYYYMM_surf_nolev.nc
- MOM6 forcing file for year YYYY and month MM
- ✔
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@DeniseWorthen @NickSzapiro-NOAA Is this file still used by CICE? The description indicates that despite the name, it's a MOM6 forcing file.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry ... where do you see this is related to CICE? Usage in RTs seems more CDEPS docn ocn_data

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oops, you're right! I scrolled up too far. It was a CDEPS thing; wondering if it still is.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I imagine these are SSTs from a Hycom run and are now "data" input coupled to ATM in RT

Comment on lines 381 to -393
@@ -390,7 +389,7 @@ Lastly, the :wm-repo:`test configuration file <blob/develop/tests/tests/hafs_reg
export INPUT_NML=input_regional_hafs.nml.IN
export MODEL_CONFIGURE=model_configure_hafs.IN
export UFS_CONFIGURE=ufs.configure.hafs_atm_ocn_wav.IN
export FV3_RUN="hafs_fv3_run.IN hycom_hat10_run.IN hafs_ww3_run.IN"
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think in this section of the docs, you actually need to copy-paste from a different test because the test that this sample is based on (hafs_regional_atm_ocn_wav) is getting deleted in Denise's PR, and even if it weren't, you probably can't just omit that file. It would likely need a replacement, tho I'd have to look into it further.
Her PR adds: tests/tests/hafs_regional_storm_following_1nest_atm_ocn_wav_mom6_debug
So maybe you could look at the configuration for that one?

@gspetro-NOAA gspetro-NOAA added documentation Improvements or additions to documentation No Baseline Change No Baseline Change labels Mar 20, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation No Baseline Change No Baseline Change

Projects

Status: Evaluating

Development

Successfully merging this pull request may close these issues.

Purge HYCOM

4 participants